Hi @GamzeUnlu95, thanks for this PR :)
Did you know that the tools that perform the Code quality Test can be set up to run automatically, so that you don't really have to think about them again and this test doesn't slow down your workflow? If you tell me which editor you are using, I can help you with that :)

The branch also needs a rebase on to main, you can do that here or locally on your computer. In the first case, you would need to pull this PR after the rebase back to your machine; whereas in the second case you would have to force push your local changes after the rebase to this PR. If you don't feel comfortable doing either, please let me know 😃

@macflo8 @GamzeUnlu95 @glatterf42 as I understand, this was superseded by #188 and #189.

The key question is: is there anything remaining on this branch that was not included in those PRs, yet should be preserved on main?

• If yes, I would suggest to mention as 1 or more comments/checklist items on Test and improve .model.material #194.
  • These could be linked to this branch, or their original location on a message_data branch.
• Whether yes or no, we can then close this PR (without merging), and possibly delete the associated branch.

I think there are no changes that need to be carried over from this branch, but I will check and confirm whether we can close this PR or need to add items to #194.

As discussed at today's MESSAGE meeting:

• This branch is marked as archived (no deletion, no pushes, etc.) using this rule.
• We will record the existence of the PR/branch for future reference, in case there is a need to come back to it: Update MESSAGEix-Materials with new steel technologies  #218 (comment)